|
Command |
Description |
|---|---|
|
hostname |
List hostname of the server |
|
ping |
Availability of the destination server over the network Ex: ping www.google.com |
|
wget |
Download packages / Softwares into a Linux system
Ex: wget <linux_downloadable_url> |
|
ifconfig |
List’s IP address of the server Ex: ifconfig / ifconfig -a |
|
telnet |
Connect to remote host / Check the port availability Ex: telnet localhost 8081 |
|
curl |
Access the application Ex: curl www.google.com |
Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...
Comments
Post a Comment